Fixed naming the shared library for debug and release builds. #179
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Seems to work now. Adding the
debug_and_releasetoken toCONFIGmight impact other workflows, so it needs to be tested on your configuration. But I think it is an improvement since it keeps all of the intermediate artifacts (object files, etc.) in one build configuration separate from the other configurations.However, I discovered that if you already have a custom build directory which switches on
{BuildConfig:name}in Qt Creator settings, as I do, you can also leave it out. But you need theCONFIG(debug,debug|release)switch to keep oneTARGETspecification from overwriting the other.If you want to try out the
OBJECTS_DIR = ./.obj, etc. suggestion, I can create another pull request for that.